Systems and methods to provide information

ABSTRACT

Systems and methods are to provide information to facilitate online transactions via mobile communications. In one aspect, a system includes a data storage facility to store and associate personal information of a user with a telephone number of the user, and an interchange coupled with the data storage facility. The interchange includes a common format processor and a plurality of converters to interface with a plurality of different controllers of mobile communications. The converters are configured to communicate with the common format processor in a common format and to communicate with the controllers in different formats. The interchange uses the converters to communicate with the mobile phone of a user to approve the providing of the personal information from the data storage facility to a website.

The present application is a continuation application of U.S. patentapplication Ser. No. 12/406,573, filed on Mar. 18, 2009, which claimspriority to Provisional U.S. Patent Application Ser. No. 61/156,858,filed Mar. 2, 2009 and entitled “Systems and Methods to ProvideInformation,” the disclosures of which are hereby incorporated herein byreference.

FIELD OF THE TECHNOLOGY

At least some embodiments of the disclosure relate to mobilecommunications in general and, more particularly but not limited to,mobile communications to facilitate online transactions.

BACKGROUND

Short Message Service (SMS) is a communications protocol that allows theinterchange of short text messages between mobile telephone devices. SMSmessages are typically sent via a Short Message Service Center (SMSC) ofa mobile carrier, which uses a store-and-forward mechanism to deliverthe messages. When a mobile telephone is not reachable immediately forthe delivery of the message, the SMSC stores the message for laterretry.

SMS messages can be sent via gateways. Some gateways function asaggregators. An aggregator typically does not have the capacity todeliver the messages directly to the mobile phones. An aggregatortypically interfaces with and relies upon the SMSC of a mobile carrierto deliver SMS messages.

Some gateways function as providers that are capable of sending textmessages to mobile devices directly, without going through the SMSC ofother mobile operators.

Text messaging between mobile telephones can also be performed usingother protocols, such as SkyMail and Short Mail in Japan.

Some mobile carriers provide email gateway services to allow textmessages to be sent to mobile phones via email. For example, anon-subscriber of the mobile carrier may send a message to an emailaddress associated with a mobile phone of a subscriber of the mobilecarrier to have the message delivered to the mobile phone via textmessaging.

Emails can also be sent to mobile telephone devices via standard mailprotocols, such as Simple Mail Transfer Protocol (SMTP) over InternetProtocol Suite (commonly TCP/IP, named from two of the protocols: theTransmission Control Protocol (TCP) and the Internet Protocol (IP)).

Short messages may be used to provide premium services to mobile phones,such as news alerts, ring tones, etc. The premium content providers maysend the messages to the SMSC of the mobile operator using a TCP/IPprotocol, such as Short Message Peer-to-peer Protocol (SMPP) orHypertext Transfer Protocol, for delivery to a mobile phone; and themobile phone is billed by the mobile operator for the cost of receivingthe premium content.

Premium services may also be delivered via text messages initiated fromthe mobile phone. For example, a televoting service provider may obtaina short code to receive text messages from mobile phones; and when theuser sends a text message to the short code, the mobile carrier routesthe message to the televoting service provider and charges the user afee, a portion of which is collected for the televoting serviceprovider.

SUMMARY OF THE DESCRIPTION

Systems and methods to provide information to facilitate onlinetransactions via mobile communications are described here. Someembodiments are summarized in this section.

In one aspect, a system includes: a data storage facility to store andassociate personal information of a user with a telephone number of theuser; and an interchange coupled with the data storage facility. Theinterchange includes a common format processor and a plurality ofconverters to interface with a plurality of different controllers ofmobile communications. The converters are configured to communicate withthe controllers in different formats; and the converters are configuredto communicate with the common format processor in a common format tofacilitate electronic payment transactions using the account identifier.

In one embodiment, the common format processor is configured to instructa first controller of the controllers, via a first converter of theconverters, to communicate with a telephone at the telephone number ofthe user to approve the providing of the personal information from thedata storage facility to a website.

In another aspect, a method includes: receiving at a server computer aweb request that includes a phone number of a user and that relates to atransaction at a third party website; based on the phone number of theuser, identifying user information stored on a data storage facilitycoupled to the server computer; and providing the user information to athird party website.

The disclosure includes methods and apparatuses which perform thesemethods, including data processing systems which perform these methods,and computer readable media containing instructions which when executedon data processing systems cause the systems to perform these methods.

Other features will be apparent from the accompanying drawings and fromthe detailed description which follows.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments are illustrated by way of example and not limitation inthe figures of the accompanying drawings in which like referencesindicate similar elements.

FIG. 1 shows a system to facilitate online transactions according to oneembodiment.

FIG. 2 shows an interchange to route messages according to oneembodiment.

FIG. 3 shows a message processor according to one embodiment.

FIG. 4 shows a method to facilitate an online transaction using aninterchange according to one embodiment.

FIG. 5 illustrates a user interface to associate an account with atelephone number according to one embodiment.

FIG. 6 illustrates another user interface to associate an account with atelephone number according to one embodiment.

FIG. 7 illustrates a user interface to initiate a payment transactionaccording to one embodiment.

FIG. 8 illustrates a user interface to initiate a payment requestaccording to one embodiment.

FIG. 9 illustrates a user interface to confirm a payment requestaccording to one embodiment.

FIG. 10 illustrates a user interface to confirm the completion of apayment transaction according to one embodiment.

FIG. 11 illustrates a way to redirect a payment confirmation accordingto one embodiment.

FIG. 12 illustrates a user interface to receive payment optionsaccording to one embodiment.

FIG. 13 shows a method to process an online payment according to oneembodiment.

FIG. 14 shows another method to facilitate a payment transactionaccording to one embodiment.

FIGS. 15-18 show methods to approve a payment transaction according tosome embodiments.

FIG. 19 shows a user interface to provide user information in connectionwith payment processing according to one embodiment.

FIG. 20 shows a user interface to provide user information to facilitatepayment processing according to one embodiment.

FIGS. 21 and 22 illustrate user interfaces for authentication accordingto some embodiments.

FIG. 23 shows a method to provide information according to oneembodiment.

FIG. 24 shows a data processing system, which can be used in variousembodiments.

DETAILED DESCRIPTION

The following description and drawings are illustrative and are not tobe construed as limiting. Numerous specific details are described toprovide a thorough understanding. However, in certain instances, wellknown or conventional details are not described in order to avoidobscuring the description. References to one or an embodiment in thepresent disclosure are not necessarily references to the sameembodiment; and, such references mean at least one.

Reference in this specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the disclosure. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment, nor are separate or alternative embodimentsmutually exclusive of other embodiments. Moreover, various features aredescribed which may be exhibited by some embodiments and not by others.Similarly, various requirements are described which may be requirementsfor some embodiments but not other embodiments.

In one embodiment, an interchange is used to interface with a pluralityof different controllers of mobile communications, such as SMS messages.The interchange can be used to associate account information with phonenumbers to facilitate electronic payments via mobile devices, such ascellular phones. The interchange is configured to communicate with themobile phones through the different controllers to provide security andconvenience for online transactions.

FIG. 1 shows a system to facilitate online transactions according to oneembodiment. In FIG. 1, an interchange (101) is provided to interfacewith a plurality of different controllers (115) for communications withthe mobile phones (117) over the wireless telecommunications network(105).

In FIG. 1, a data storage facility (107) stores user account information(121) and the corresponding phone numbers (123) of the mobile phones(117). The interchange (101) is coupled with the data storage facility(107) to communicate with the mobile phones (117) at the correspondingphone numbers (123) to confirm operations that are performed using theaccount information (121). Since the account information (121) issecured by the interchange (101), the account information (121) can beused to pay for products and services offered by the servers (113) ofvarious merchants, without being revealed to the merchants.

In one embodiment, the server (113) offers products and/or servicesadapted for a virtual world environment, such as an online gameenvironment, a virtual reality environment, etc. The products may bevirtual goods, which can be delivered via the transmission of data orinformation (without having to physically deliver an object to theuser). For example, the virtual goods may be a song, a piece of music, avideo clip, an article, a computer program, a decorative item for anavatar, a piece of virtual land in a virtual world, a virtual object ina virtual reality world, etc. For example, an online game environmenthosted on a server (113) may sell services and products via points orvirtual currency, which may be consumed by the user while engaging in agame session. For example, a virtual reality world hosted on a server(113) may have a virtual currency, which may be used by the residents ofthe virtual reality world to conduct virtual commerce within the virtualreality world (e.g., buy virtual lands, virtual stocks, virtual objects,services provided in the virtual reality world, etc). In otherembodiments, the server (113) may also offer physical goods, such asbooks, compact discs, photo prints, postcards, etc.

In FIG. 1, the interchange (101) may communicate with differentcontrollers (115) of mobile communications via different networks (e.g.,105 and 103) and/or protocols. The interchange (101) processes therequests in a common format and uses a set of converters forcommunications with the different controllers (115) respectively.

For example, the controllers (115) may be different aggregators,providers and/or SMSCs of different mobile carriers. Based on the phonenumbers (123), the interchange (101) interfaces with the correspondingcontrollers (115) to communicate with the mobile phones (117) via textmessaging to confirm the operations related to the corresponding accountinformation (121), such as bank accounts, credit card numbers, chargecard numbers, etc.

In FIG. 1, the user terminals (111) may use a unified interface to sendrequests to the interchange (101). For example, a website of theinterchange (101) may be used to receive the account information (121)from the web browsers running in the user terminals (111). The userterminals (111) are typically different from the mobile phones (117).However, in some embodiments, users may use the mobile phone (117) toaccess the web and submit the account information (121). Alternatively,the users may use the mobile phone (117) to submit the accountinformation (121) to the interchange (101) via text messaging, email,instant messaging, etc.

The use of the mobile phones (117) in the confirmation of activitiesthat involve the account information (121) increases the security of thetransaction, since the mobile phones (117) are typically secured in thepossession of the users.

Further, in one embodiment, the interchange (101) may use the phonebills of the mobile phones (117) to pay for purchases, in order to usethe account information (121) to pay for the phone bills, and/or todeposit funds into the accounts identified by the account information(121) by charging on the phone bills of the corresponding mobile phones(117). In some embodiments, the accounts identified by the accountinformation (121) are hosted on the data storage facility (107). Inother embodiments, the accounts are hosted on the account servers (125)of financial institutions, such as banks, credit unions, credit cardcompanies, etc.

In one embodiment, once the account information (121) is associated withthe mobile phones (117) via their phone numbers (123) stored in the datastorage facility (107), the users may use the user terminals (111) toaccess online servers (113) of various merchants or service providers tomake purchases. From the user terminals (111), the users can use theaccounts identified by the account information (121) to make the paymentfor the purchases, without revealing their account information (121) tothe operators of the servers (113).

In one embodiment, the mobile phones (117) are used by the correspondingusers to make payments and/or manage funds, such as for making purchasesin various websites hosted on the servers (113) of merchants and serviceproviders and/or for transferring funds to or from an account identifiedby the account information (121), such as phone bills of land-linetelephone services, credit card accounts, debit card accounts, bankaccounts, etc., or an account hosted on the data storage facility (107)or telecommunication accounts of the mobile phones (117) withtelecommunication carriers. The mobile phones (117) are used to confirmand/or approve the transactions associated with the account identifiedby the account information (121) (or other accounts). The interchange(101) interfaces the mobile phones (117) and the servers (113) toconfirm and/or approve transactions and to operate on the accountidentified by the account information (121) (and/or other accountsassociated with the phone number (123)).

For example, the user terminal (111) may provide the phone numbers (123)to the servers (113) to allow the servers (113) to charge the accountidentified by the account information (121) associated with the phonenumber (123). The interchange (101) sends a message to the mobile phone(117) via the phone number (123) to confirm the payment request. Oncethe payment is confirmed or approved via the corresponding mobile phone(117), the interchange (101) charges the account identified by theaccount information (121) (e.g., by communicating with the accountserver (125) on which the corresponding accounts are hosted) and paysthe server (113) on behalf of the user, using the funds obtained fromthe corresponding account identified by the account information (121).

In one embodiment, the user terminal (111) may not even provide thephone number (123) to the server (113) to process the payment. Theserver (113) may redirect a payment request to the interchange (101),which then prompts the user terminal (111) to provide the phone number(123) to the website of the interchange (101) to continue the paymentprocess.

For example, the server (113) may redirect the payment request to thewebsite of the interchange (101) with a reference indicating thepurchase made via the user terminal (111). The interchange (101) can usethe reference to subsequently complete the payment with the server (113)for the purchase, after receiving the phone number (123) directly fromthe user terminal (111) to confirm the payment via the mobile phone(117).

In some embodiments, instead of directly providing the phone number(123) to identify the account information (121), the user may provideother information to identify the phone number (123), such as an accountidentifier of the user assigned to the user for obtaining the servicesof the interchange (101).

In one embodiment, the account information (121) is pre-associated withthe phone number (123) prior to the payment request. The accountinformation (121) may be submitted to the interchange (101) via the userterminal (111) or the mobile phone (117) via a secure connection.

Alternatively, the user may supply the account information (121) to theinterchange (101) at the time the payment request is submitted from theuser terminal (111) to the interchange (101). Alternatively, the usermay supply the account information (121) to the interchange (101) at thetime the user responds to the confirmation message for the paymentrequest.

In some embodiments, the user may supply the account information (121)after a transaction using funds collected via the telecommunicationcarrier of the mobile phone (117) at the phone number (123). Forexample, after the transaction, the interchange (101) may send aninvitation message, such as a text message to the mobile phone (117) atthe phone number (123), to the user to invite the user to register withthe interchange (101) and provide the account information (121). Theuser may register with the interchange (101) via the mobile phone (117)(e.g., by a replying text message), or via a web page of the interchange(101) (e.g., using a link and/or a unique code provided in theinvitation message).

After the user registers with the interchange (101) (e.g., via themobile phone (117) and by providing the account information (121)), theuser may create a customized personal identification number (PIN) orreceive a PIN for enhanced security. Using the PIN, the user may use theaccount information (121) to complete an online transaction withouthaving to confirm and/or approve a transaction using the mobile phone(117). In some embodiments, the PIN may be used to reduce unwantedmessages to the mobile phone (117). For example, once the phone number(123) and the account information (121) are associated with a PIN, theinterchange (101) may require the user of the user terminal (111) toprovide the correct PIN to initiate the payment process. Thus, a spammerhaving only the phone number (123) (or a different user mistakenly usingthe phone number (123)) may not successfully use the user terminal (111)to request the interchange (101) to send confirmation messages to themobile phone (117) protected by the PIN. In some embodiments, theinterchange (101) may offer further incentives to the user forregistering with the interchange (101), such as reduced fees, discounts,coupons, free products and services, etc.

In one embodiment, once the account information (121) is associated withthe phone number (123) in the data storage facility (107), the user doesnot have to resubmit the account information (121) in subsequent paymentrequests.

By delegating the payment task to the interchange (101) and securing theaccount information (121) in the data storage facility (107), the systemas shown in FIG. 1 can increase the security of using the accountinformation (121) in an online environment.

In some embodiments, the interchange (101) can also fulfill the paymentrequests using the funds collected via the phone bill of the phonenumbers (123). The interchange (101) can collect the funds via sendingpremium messages to the mobile phones (117) at the phone numbers (123),after receiving confirmation from the mobile phone (117).

For example, after the confirmation or approval message is received fromthe mobile phone (117), the interchange (101) performs operations tocollect funds via the phone bill of the phone number (123). Theinterchange (101) may calculate the required premium messages to bill tothe mobile phone (117). For example, mobile terminated premium SMSmessages may have a predetermined set of prices for premium messages.The interchange (101) determines a combination of the premium messagesthat has a price closest to the amount required by the transaction, andsends this combination of premium messages to the mobile phone (117).For example, mobile originated premium SMS messages may also have apredetermined set of prices for premium messages. The interchange (101)can calculate the set of messages required for the transaction andtransmit a text message to the mobile phone (117) of the user toinstruct the user to send the required number of premium messages toprovide the funds.

In one embodiment, the data storage facility (107) stores thetransaction history (127) associated with the phone number (123) anduses the transaction history (127) to approve payment requests and toreduce the time period for processing a subsequent payment request.

For example, from the transaction history (127) the interchange (101)may identify a pattern of prior payment requests made via the phonenumber (123) and match subsequent requests with the identified pattern.When a subsequent request matches the pattern, the interchange (101) mayskip the communication with the mobile phone (117) at the phone number(123), which communication is otherwise performed after the paymentrequest and before the payment operation for payment confirmation and/orapproval. Skipping such a communication between the payment request andthe payment operation can reduce the time period for payment processingand improve user experience.

Examples of transaction patterns may include the use of the individualuser terminals (111), the typical time period of payment requests, rangeof payment amounts, and/or certain characteristics of payees, such as acollection of frequently used payees, payees who provide certain typesof products or services, the geographical region of payees, etc.

In one embodiment, when the subsequent payment request is receivedwithin a predetermined time limit of a previous confirmed paymentrequest from the same user terminal (111), the interchange (101) mayapprove the payment request without communicating with the mobile phone(117) at the phone number (123) for approval or confirmation.

In one embodiment, when the interchange (101) skips the communicationwith the mobile phone (117) at the phone number (123) for approval orconfirmation and approves a transaction request based on the transactionhistory (127), the interchange (101) may send a notification message tothe mobile phone (117) at the phone number (123) for enhanced securitybut not requiring a response from the user. If the user determines thatthe notification message corresponds to an unauthorized use of the phonenumber (123), the user may reply to the notification message from themobile phone (117) to report the unauthorized use and/or stop or reversethe payment operation.

In some embodiments, the user may start a session (e.g., a web session)authenticated using a password associated with the phone number (123),prior to the payment request. When the payment request is made withinthe authenticated session (e.g., before the user logs off the session,or before the session times out), the interchange (101) may skip theconfirmation/approval communication with the mobile phone (117) at thephone number (123) to reduce the time period for payment processing.

In one embodiment, the session is authenticated via communications withthe mobile phone (117) at the phone number (123). For example, after theuser provides the phone number (123) to log into a session on a userterminal (111), the interchange (101) may generate a code (e.g., a codefor one time use) and send the code to the user via the user terminal(111) (or the mobile phone (117) at the phone number (123)). Theinterchange (101) then requests the code back from the user via themobile phone (117) at the phone number (123) (or the user terminal(111)), which is not used to send the code. When the code sent by theinterchange (101) matches the code received back from the user, theassociation between the user terminal (111) and the mobile phone (117)at the phone number (123) can be established; and the identity of theuser of the user terminal (111) can be confirmed. Such confirmation canbe logged in the transaction history (127) for subsequent approval ofpayment requests.

In one embodiment, the user may specify a time period for the session,or the time period for the association between the user terminal (111)and the phone number (123). The user may specify the time period usingthe user terminal (111) when providing the phone number (123) toinitiate the session, or specify the time period using the mobile phone(117) when providing the one-time code back to the interchange (101).During the time period of the confirmed association between the userterminal (111) and the phone number (123), a payment request from theuser terminal (111) can be automatically identified with the phonenumber (123) without the user having to explicitly specify the phonenumber (123) for the payment request. Alternatively, for enhancedsecurity and/or flexibility, the interchange (101) may require the userto identify the phone number (123) in the payment request, even thoughthe payment request is from the user terminal (111) that is associatedwith the phone number (123).

In one embodiment, the code for the authentication of the session can becommunicated to and/or from the mobile phone (117) via short messageservice (SMS), voice message, voice mail, or other services, such asemail, instant messaging, multimedia messaging service (MMS), etc.

In one embodiment, after the user provides the phone number (123) to loginto a session on a user terminal (111), the interchange (101) providesa message to the mobile phone (117) at the phone number (123) andreceives a reply to the message from the mobile phone (117) within apredetermined period of time to authenticate the session and associatethe user terminal (111) with the phone number (123). If the reply is notreceived from the mobile phone (117) with the predetermined period oftime, the session is not authenticated.

In one embodiment, the user may provide an advance approval forsubsequent payment requests to pay via the phone number (123). Theadvance approval may include a number of limitations, such as the timelimit for the expiration of the advance approval, the budget limit forthe advance approval, a limit on payees for the advance approval, etc.For example, the advance approval may limit the payees based on theirbusiness category, web address, product type, service type, geographiclocation, etc. For example, the budget limit may include the frequencyof subsequent payment requests, limit for individual payment requests,and total limit for subsequent payment requests, etc.

In one embodiment, the advance approval is specific for a user terminal.For example, the advance approval may be obtained via communicationswith the user via both a specific user terminal (111) and the mobilephone (117) at the phone number (123). Thus, the advance approvalapplies only to subsequent payment requests from the specific userterminal (111) identified by the advance approval.

Alternatively, the advance approval may not be limited to a specificuser terminal (111). The advance approval may be used for any userterminals (111) used by the user of the phone number (123) to requestpayments via the phone number (123). In some embodiments, the advanceapproval is limited to user terminals (111) of certain characteristicsidentified by the advance approval, such as a geographic region of theuser terminal (111) (e.g., determined based on the communicationaddresses, routing paths, access points for wireless connections, basestations for cellular communications, etc.). In some embodiments, theinterchange (101) automatically identifies these characteristics basedon the communications to obtain the advance approval (e.g., based ontransaction history (127)), without the user explicitly specifying thecharacteristics.

In one embodiment, the data storage facility (107) also stores userinformation (129) associated with the phone number (123). Whenauthorized, the interchange (101) provides the user information (129) tothe servers (113) to facilitate transactions between the user terminals(111) and the servers (113).

For example, the user information (129) may include shipping address,billing address, user preferences, login credentials, etc. In someembodiments, the interchange (101) may also provide the accountinformation (121) to the server (113) to allow the server (113) tocharge the user using the account information (121). Thus, the accountinformation (121) may also be considered as part of the user information(129) in some embodiments.

In one embodiment, after a request for payment to a merchant isconfirmed/approved via the mobile phone (117) at the phone number (123),the interchange (101) provides the server (113) with the userinformation (129) that is associated with the phone number (123) in thedata storage facility (107), to provide assistance in the transaction.For example, the user may store the shipping address as part of the userinformation (129) associated with the phone number (123) on the datastorage facility (107). After the interchange (101) finishes processingthe payment request, the interchange (101) may provide the shippingaddress to the server (113) to allow the merchant to ship a product tothe user; thus, the user does not have to manually submit the shippingaddress to various servers (113).

In one embodiment, after a request is confirmed/approved via the mobilephone (117) at the phone number (123), the interchange (101) may provideat least a portion of the account information (121) to the server (113)to allow the server (113) to process the payment using the accountinformation (121). For example, the interchange (101) may provide theaccount identifier (e.g., a credit card number, a bank account number, adebit card number), or a portion of the account identifier, to theserver (113) to allow the server (113) to charge the user using theaccount identifier. Thus, the user does not have to manually supply thecorresponding information to the server (113). In one embodiment, theentire account identifier is provided to the server (113) for theconvenience of the user. In one embodiment, a partial account identifieris provided to the server (113) to balance convenience and security; andthe user provides the remaining portion of the account identifierdirectly to the server (113) to complete the transaction. In someembodiments, the interchange (101) provides the server (113) withinformation related to account type, expiration date, billing address,etc. to assist the user in the check out process on the server (113). Insome embodiments, the interchange (101) does not provide the accountidentifier to the server (113) for improved security; and the server(113) obtains the account identifier from the user directly and obtainsother information, such as account type, expiration date, billingaddress, etc. from the interchange (101).

In one embodiment, the interchange (101) dynamically determines theamount of information that is provided to the server (113). For example,the decision may be based on matching the current transaction with apattern of past transactions (e.g., determined based on the transactionhistory (127)) and/or the security levels at the server (113). Whenthere is a match, some of the information that is not otherwise providedmay be provided from the interchange (101) to the server (113), such asa portion of the account information (121).

In some embodiments, the interchange (101) provides the information tothe server (113) based on an advance approval obtained from the mobilephone (117), or based on an approval decision made based on thetransaction history (127).

In one embodiment, the interchange (101) provides the user information(129) to sign into an authenticated session with the server (113). Insome embodiments, the authenticated session is associated with theinterchange (101) and/or used as an advance approval for paymentrequests occurring in the session.

FIG. 2 shows an interchange to route messages according to oneembodiment. In FIG. 2, the interchange (101) includes a unified datainterface (135) for interaction with the servers (113). The servers(113) may redirect the payment requests to the interchange (101) toallow the interchange (101) to subsequently communicate with the user toprocess the payment request, including obtaining payment options andidentifying user accounts (123), before returning to communicating withthe server (113). Alternatively, the servers (113) may collect accountrelated information (e.g., the phone number of the user) to requestpayment from the interchange (101).

In FIG. 2, the interchange (101) includes a common format processor(133), which processes various payment options in a common format. Inone embodiment, the common format processor (133) can handle thepayments via mobile terminated text message, mobile originated textmessage, operator bill, credit card, stored value account, and otheronline payment options. The common format processor (133) determines theactual amount that is to be billed to the user, based on the paymentoptions (e.g., mobile terminated premium SMS, mobile originated premiumSMS, operator billing, credit cards, etc.), and selects a converter(131) to communicate with a corresponding controller (115).

Different converters (131) are configured to communicate withcorresponding controllers (115) in different languages and protocols.The converters (131) perform the translation between the common formatused by the common format processor (133) and the corresponding formatsused by the controllers (115).

The use of the common format processor (133) simplifies the structure ofthe interchange (101) and reduces the development effort required forthe interchange (101) to interface with the increasing number ofdifferent controllers, such as SMSC, mobile providers, aggregators,gateways, etc.

FIG. 3 shows a message processor according to one embodiment. In FIG. 3,the common format processor (133) includes a billing engine (157) thatcalculates the amount to be billed to the user, by adding or subtractingtransaction costs for different billing methods, such as mobileterminated text message, mobile originated text message, operatorbilling, credit card, stored value account, and other online paymentoptions.

In one premium message billing method, the interchange (101) sendsmobile terminated premium SMS messages to the mobile phone (117) to billthe user, or requests the mobile phone (117) to send mobile originatedpremium SMS messages to a short code representing the interchange (101).

In one operator billing method, the interchange (101) directly sends amessage to the mobile carrier of the mobile phone (117) to bill theamount on the phone bill of the mobile phone (117), without having tosend a premium message to the mobile phone (117).

The common format processor (133) includes a decision engine (151) whichdecides how to generate a set of one or more messages to the mobilephone (117) based on a set of rules (141), regulations (143), limits(145), records (147) and restrictions (149).

For example, different countries have different regulations (143)governing the mobile communications with the mobile phones (117). Forexample, different mobile carriers have different rules (141) regardingpremium messages. For example, past transaction records (147) can beused to monitor the transactions to discover suspected fraudulentactivities. For example, parental limits (145) and merchant restrictions(149) can be imposed.

Based on results of the decision engine (151), the mobile messagegenerator (153) generates one or more messages to communicate with themobile phone (117) about the transaction (e.g., a request to collectfunds via the phone bill of the user for a payment request, or fordeposit into an account identified by the account information (121)).The converter (131) then interfaces with the corresponding controller(115) to transmit the messages to the mobile phones (117).

FIG. 4 shows a method to facilitate an online transaction using aninterchange according to one embodiment. In FIG. 4, the user terminal(111) provides (171) account information (121) to the interchange (101)for association with the phone number (123). For example, the user mayuse a device running a web browser as the user terminal (111) to submitthe account information (121) via a secure web connection. The userterminal (111) is typically different from the mobile phone (117).However, in some embodiments, the mobile phone (117) may also be used asthe user terminal (111) to submit the account information (121) (e.g.,via a wireless application protocol (WAP) application, or via a messagesent via short message service (SMS) or multimedia message service(MMS), or via an email message or an instant message).

After the user provides the account information (121) to the interchange(101) for storage in the data storage facility (107), the user can send(177) a charge request to the server (113) of a merchant from the userterminal (111). The server (113) of the merchant can send or redirect(179) the charge request to the interchange (101). In response to thecharge request, the interchange (101) sends (173) a confirmation messageto the mobile phone (117). If the user sends (173) an approval, or anappropriate reply, to the confirmation message from the mobile phone(117), the interchange (101) communicates with the account server (125)to charge an account of the user identified by the account information(121), without revealing the account information (121) to the server(113). The interchange (101) pays the merchant on behalf of the userusing the funds collected via charging the account of the user. Forexample, the interchange (101) may use its own bank account to pay themerchant operating the server (113). Thus, the financial information ofthe user is not revealed to the merchant.

Upon the completion of the payment process, the interchange (101) cannotify the user via the mobile phone (117) and/or the user terminal(111).

In some embodiments, the server (113) of the merchant redirects thecharge request to allow the user terminal (111) to communicate with theinterchange (101) to continue the payment process; and the user terminal(111) may provide (171) the account information (121) directly to theinterchange (101) after the charge request is redirected.

In alternative embodiments, the user may provide the account information(121) from the mobile phone (117) together with the approval of thecharge request.

In one embodiment, the interchange (101) communicates with the mobilephone (117) for the confirmation of the charge request via SMS messages.Alternatively, the confirmation and approval messages can be sent (173)via emails, instant messages, voice message, live calls from operators,etc.

In some embodiments, the user of the mobile phone (117) may choose tofulfill the charge request via the phone bill, instead of charging theaccount identified by the account information (121). Thus, after theconfirmation, the interchange (101) sends the premium messages to themobile phone (117) to collect funds via the phone bill of the mobilephone (117). In other embodiments, the interchange (101) may send aninstruction with the confirmation message to the mobile phone (117) toinstruct the user to send mobile originated premium messages to theinterchange (101) to collect the funds via the phone bill of the mobilephone (117).

FIG. 5 illustrates a user interface to associate an account with atelephone number according to one embodiment. In FIG. 5, the userinterface (180) includes a text field (183) that allows the user tospecify the phone number (123) with which the account information (121)provided in the text field (181) is to be associated.

In FIG. 5, the user interface (180) further includes an option list,which allows the user to select various types of accounts, such ascredit card accounts, bank accounts, charge card accounts, etc. In theexample illustrated in FIG. 5, the checkbox (185) is selected to specifya credit card account.

In some embodiments, the user interface (180) may further present a textfield (not shown in FIG. 5) to allow the user to specify an alias forthe account information (121) supplied in the text input field (181).For enhanced security, the alias can be used for subsequentcommunications with the user without revealing the account information(121).

In FIG. 5, the user interface (180) may be presented via a web browser(or a custom application) to submit account information (121) in thetext input field (181) from a user terminal (111) to the interchange(101). Alternatively, the account number can be submitted from themobile phone (117) via a message sent via SMS, WAP, voice mail, or viaan interactive voice response (IVR) system.

In one embodiment, the server (113) presents the payment option (185)via an online shopping cart system or a third party checkout system.Alternatively or in combination, the server (113) presents the paymentoption (185) via a web widget. For example, a web widget may include aprogram code that is portable and executable within a web page withoutrequiring additional compilation. The web widget allows the user toselect the option (185) to pay for the product and/or service withoutleaving the web page or refreshing the web page. In one embodiment, theinterchange (101) provides the web widget to facilitate the paymentprocessing.

FIG. 6 illustrates another user interface to associate an account with atelephone number according to one embodiment. In FIG. 6, the userinterface (190) is presented on the mobile phone (117) of the user. Theuser interface (190) presents a message (191) from the interchange (101)to the mobile phone (117) at the phone number (123). The message (191)prompts the user to submit the account information (121) by providing areply message (193). The user may select the “send” button (195) toprovide the account information (121) for association with the phonenumber (123) or select the “cancel” button (197) to ignore the prompt.

In one embodiment, the messages (191 and 193) are transmitted to themobile phone (117) via a short message service (SMS). Alternatively, themessages can be transmitted to the mobile phone (117) via otherprotocols, such as multimedia message service (MMS), email, instantmessaging, WAP, voice mail, voice messages via an interactive voiceresponse (IVR) system, etc.

FIG. 7 illustrates a user interface to initiate a payment transactionaccording to one embodiment. In FIG. 7, the user interface (201)provides an option (205) to request the interchange (101) to process thepayment for the amount (203) required to make a purchase from the server(113) of a merchant.

In one embodiment, after the user selects the payment option (205), theserver (113) directs the request to the web server of the interchange(101), with a set of parameters to indicate the amount (203), theidentity of the merchant, a reference to the purchase, etc. Thus, theuser does not have to provide any personal information to the server(113) of the merchant to complete the payment process.

Alternatively, the user may provide the phone number (123) to themerchant to process the payment. Thus, the user does not have to visitthe website of the interchange (101) to complete the payment.

FIG. 8 illustrates a user interface to initiate a payment requestaccording to one embodiment, after the payment request is redirected tothe website of the interchange (101). In FIG. 8, the user interface(201) includes the identity of the merchant and the amount (203) of therequested payment. The user interface (201) includes a text field (183)to allow the user to provide the phone number (123) to identify theaccount information (121) via its association with the phone number(123) in the data storage facility (107).

Further, user authentication may be used to reduce false messages to thephone number (123). For example, the user interface (201) may request aPIN for enhanced security. For example, the user may be required toregister with the interchange (101) prior to using the services of theinterchange (101); and after registering with the interchange (101), theuser is provided with the PIN or can created a customized PIN to accessthe functionality provided by the user interface (201).

Alternatively, the user interface (201) may request an identifierassociated with the phone number (123) to initiate the paymenttransaction. In some embodiments, the user interface (201) requires theuser to provide no information other than the phone number (123) in thetext field (183) to initiate the transaction.

In FIG. 8, the user interface (201) allows the user to select one optionfrom a plurality of payment options, including paying via the phonebill, and paying via one or more of the accounts identified by theaccount information (121) associated with the phone number (123) in thedata storage facility (107).

In some embodiments, the user interface (201) may present the paymentoptions after authenticating the user (e.g., via a personalidentification number or password) for enhanced security.

In some embodiments, the user interface (201) identifies the differentaccounts represented by the account information (121) by showing aliasesof the accounts. The aliases may be previously specified by the user, orbe dynamically generated by the interchange (101) based on the types ofthe accounts and/or portions of the account information (121) (e.g., thefirst or last few digits of the account number, etc.)

In one embodiment, once the user submits the payment request via theuser interface (201), the interchange (101) transmits a confirmationmessage to the mobile phone (117) according to the phone number (123)provided in the text field (183). In one embodiment, the interchange(101) transmits the confirmation to the mobile phone (117) after theuser is authenticated via the user interface (201) to reduce thepossibility of unauthorized/unwelcome messages to the mobile phone(117), which may occur when the user intentionally or unintentionallyprovides an unrelated phone number in the entry box (183).

FIG. 9 illustrates a user interface to confirm a payment requestaccording to one embodiment. In FIG. 9, the confirmation message (217)includes the amount (203) of the requested payment and the identity ofthe payee (e.g., a merchant operating the server (113)).

In one embodiment, the confirmation message (217) includes theinstruction to reply with a code, such as a code (e.g., “pay”) providedin the confirmation message (217) as illustrated in FIG. 9.

The presence of the code in the reply message is an indication of theuser approving the request; and the requirement for such a code in thereply eliminates false confirmations (e.g., generated via accidentalreplies or automated replies).

Alternatively or in combination, the requested code may include a PINassociated with the account, and/or a code (not shown) randomlygenerated and presented in the user interface used to initiate thepayment transaction (e.g., user interface (201)).

In some embodiments, the code requested in the text message (217) may bea personal identification number (PIN) associated with the phone number(123). The text message (217) does not include the code; and theknowledge of the code is an indication of the identity of the user.Thus, the use of such a code increases the security of the transaction.

In a further embodiment, the code requested in the text message (217)includes a code that is provided in response to the payment request(e.g., via the user interface (201), not shown in FIG. 8). The code maybe generated randomly at the time the request is received via the userinterface (201), or when the user interface (201) is presented to theuser. The code provided to the user interface (201) can be requested inthe reply received from the user interface (190) to indicate that theuser who is in possession of the mobile phone (117) has actual knowledgeabout the payment request submitted via the user interface (201).

After the correct reply is received, the interchange (101) communicateswith the account server (125) to electronically charge the user usingthe account information (121) and pays the payee using the fundscollected via communicating with the account server (125). Theinterchange (101) then notifies the user when the payment transaction iscomplete.

For example, the interchange (101) may notify the user via a textmessage to the mobile phone (117), as illustrated in FIG. 10. FIG. 10illustrates a user interface to confirm the completion of a paymenttransaction according to one embodiment. No reply to the message thatconfirms the completion of the payment transaction is necessary. Oncethe payment transaction is complete, the user would have access to theproduct purchased via the payment transaction.

In one embodiment, the interchange (101) stores an address of the userassociated with the phone number (123). After the completion of thepayment transaction, the interchange (101) provides the address to theserver (113) of the merchant for the delivery of the purchased product.In some embodiments, the user may provide multiple addresses associatedwith the phone number (123) and may select one as a delivery address inthe confirmation/approve message to the interchange (101).Alternatively, the interchange (101) may receive an address for productdelivery from the mobile phone (117) together with theconfirmation/approve message and then forward the address to the server(113) of the merchant. Thus, the shipping address of the transaction isverified to be associated with the mobile phone (117). In alternativeembodiments, the user may directly provide the shipping address in thewebsite hosted on the server (113) of the merchant.

In other embodiments, the user is provided with the options to pay viathe mobile phone bill associated with the phone number (123). Theinterchange (101) may dynamically calculate a set of premium messages,based on a set of limited number of predetermined prices for premiummessages, to match the purchase price. The interchange (101) sends theset of premium messages to the mobile phone (117) at the phone number(123) to collect the funds via the telecommunication carriers to pay forthe purchases. Thus, the purchase prices are not limited to the set ofpredetermined prices for premium messages. In some embodiments, theinterchange (101) may send the set of premium messages in a period oftime (e.g., a week, a month, a number of mouths, etc.) to spread thepayments over the period of time (e.g., to overcome budget limits and/orlimits imposed by regulations).

FIG. 11 illustrates a way to redirect a payment confirmation accordingto one embodiment. For example, after the user submits the paymentrequest to the interchange (101) via the user interface (201) shown inFIG. 8, the interchange (101) may present the user interface (201)illustrated in FIG. 11 to the user. The user interface (201) indicatesthat the request is being processed; and the user interface (201) isperiodically updated to show progress. Once the payment transaction iscompleted, the user interface (201) provides a confirmation message andmay automatically redirect the user back to the website of the payee(e.g., to access the purchased products or services).

In one embodiment, the user is required to provide the approval inresponse to the confirmation message (217), as illustrated in FIG. 9,within a predetermined period of time. If the user fails to provide theapproval from the mobile phone (117) within the predetermined period oftime, the payment request may be rejected; and the user interface (201)may present a message indicating the failure and then redirect the userback to the website of the payee.

In some embodiments, instead of redirecting the user back to the websiteof the payee after the expiration of a predetermined period of time(e.g., after the failure of the payment process, or after the completionof the payment), the user interface (201) may provide a link to thewebsite of the payee to allow the user to manually select the link to goback to the website of the payee to continue the process at the websiteof the payee.

FIG. 12 illustrates a user interface to receive payment optionsaccording to one embodiment. In FIG. 12, the interchange (101) sends amessage (217) to the mobile phone (117) to provide a number of optionsto the user. The message (217) identifies the amount (203) of therequested payment and the identity of the payee (e.g., a merchantoperating the server (113)) and asks the user to approve the paymentrequest via a reply that contains a selected payment option.

In FIG. 12, the user may reply with the code “1” to approve the paymentrequest and to pay via the phone bill of the mobile phone (117).Alternatively, the user may reply with the credit card information tocharge the payment to a credit card, as illustrated in FIG. 12.

In one embodiment, if the user provides credit card account informationin the approval message, the credit card account information is storedand associated with the phone number (123) in the data storage facility(107). Thus, in subsequent approval messages, the user does not have tosupply the same information again.

For example, the data storage facility (107) may store accountinformation for each of a plurality of account types (e.g., Visa,MasterCard, checking, savings, etc.) Thus, each of the accounts can beidentified to the user via the account type in the confirmation message,without revealing the details of the account information.

For example, the interchange (101) may combine the name of the financialinstitutions and the type of accounts to generate aliases for theaccount information.

In some embodiment, the user may define the aliases for the accountinformation by supplying the aliases with the account information (121)for association with the phone number (123).

FIG. 13 shows a method to process an online payment according to oneembodiment. In FIG. 13, the interchange (101) receives (301) an accountidentifier (e.g., 121) from a user and associates (303) the accountidentifier with a phone number (123) of the user in the data storagefacility (107). Over the Internet the interchange (101) subsequentlyreceives (305) a request for payment to be paid to a payee via themobile phone (117) identified by the phone number (123). In response tothe request, the interchange (101) transmits (307) a message (217) tothe mobile phone (117) to confirm the payment.

After receiving (309) a confirmation or approval from the mobile phone(117) for the payment, the interchange (101) electronically charges(311) the user an amount using the account identifier (e.g., viacommunicating with the account server (125) using the accountidentifier). The interchange (101) then transfers (313) the amount to apayee to fulfill the payment.

FIG. 14 shows another method to facilitate a payment transactionaccording to one embodiment. In FIG. 14, the interchange (101) receives(331) a request to pay an amount to a payee via a mobile phone (117).The interchange (101) transmits (333) a message (217) to the mobilephone (117) to confirm the request via the converter (131) correspondingto the controller (115) of the mobile phone (117).

After the interchange (101) receives (335) a confirmation with anaccount identifier (e.g., 121) from the mobile phone (117) for therequest, the interchange (101) electronically communicates (337) with afinancial institution to charge the user the specified amount using theaccount identifier. The interchange (101) pays (339) the payee accordingto the amount, optionally charges (341) the user a first fee to pay thepayee, and optionally charges (343) the payee a second fee forprocessing the payment.

In one embodiment, the users are given an incentive to provide theaccount information (121) for electronic payments via the accountservers (125). For example, the interchange (101) may charge a lower feefor fulfilling payment requests via the account server (125) than forfulfilling payments requests via the phone bill. For example, theinterchange (101) may offer rebates, discounts, etc. to the users whoprovide the account information (121). In some embodiments, theinterchange (101) can complete a payment process via the account server(125) with fewer restrictions than via the phone bill.

In one embodiment, the merchant may specify the second fee. Differentmerchants may offer different percentages of the purchase prices as thesecond fee; and the interchange (101) may calculate the first fee basedon the second fee offered by the merchant, by deducting the second feefrom the total fees to be charged (e.g., fees charged by thetelecommunication carrier for collecting the funds via the mobile phonebill associated with the phone number (123) and/or the fees charged bythe interchange (101) for processing the payments). Since the first feeis charged to the customer (e.g., the purchaser of products andservices), the cost to the customer can vary based on the selection ofthe merchant. For the same purchase prices, the first fee (and thus thecost to the customer) may be different for purchases made via differentmerchants, because the merchants may offer different percentage of thepurchase price as the second fee. In some embodiments, the first andsecond fees include both fees charged by the telecommunication carrierfor collecting the funds via the mobile phone bill/account associatedwith the phone number (123) and the fees charged by the interchange(101) for processing the payments. In some embodiments, the first feeincludes the fees charged by the telecommunication carrier but no feescharged by the interchange (101). In some embodiments, the second feeincludes the fees charged by the telecommunication carrier but no feescharged by the interchange (101). In some embodiments, the first feeand/or the second fee do not include the fees charged by thetelecommunication carrier. In some embodiments, the first fee is notcharged; and in other embodiments, the second fee is not charged.

FIGS. 15-18 show methods to approve a payment transaction according tosome embodiments.

In FIG. 15, after the interchange (101) confirms (341) an identity of auser of a user terminal (111), the interchange (101) receives (343) fromthe user terminal (111) a request to pay via a phone number (123) of theuser. In one embodiment, the interchange (101) confirms the identify ofthe user of the user terminal (111) and/or associates the identity ofthe user of the user terminal (111) with the phone number (123) of themobile phone (117) prior to the user submitting a request to pay via thephone number (123). Thus, communications with the mobile phone (117) atthe phone number (123) for the confirmation and/or approval of therequest does not have to take place between the request and the paymentoperation; and thus the delay between the request and the paymentoperation can be reduced.

For example, the user terminal (111) may include a web browser; and theuser may log into a web server of the interchange (101) using the webbrowser. The interchange (101) may prompt the user via the web browserrunning on the user terminal (111) to provide the phone number (123) anda password associated with the phone number (123). After verifying thepassword, the user is logged into a session tracked by the web browseron the user terminal (111); and the web browser running on the userterminal (111) is associated with the phone number (123).

In one embodiment, the interchange (101) further communicates with themobile phone (117) at the phone number (123) to complete theverification process. For example, the interchange (101) may send aone-time verification code to the mobile phone (117) at the phone number(123) and request the user to provide the correct one-time verificationcode back via the user terminal (111) to verify the association betweenthe user terminal (111) and the phone number (123). Alternatively, theinterchange (101) may provide the one-time verification code to the userterminal (111) and instruct the user to communicate the code back to theinterchange (101) via the mobile phone (117) at the phone number (123).Alternatively, after the user logs in using the user terminal (111), theinterchange (101) may send a message to the mobile phone (117) torequest a reply from the mobile phone (117) at the phone number (123)within a predetermined period of time to validate the session. In someembodiments, after the user provides the phone number (123) using theuser terminal (111) to the interchange (101), the user is instructed toprovide the password via the mobile phone (117) to complete the log inprocess.

In one embodiment, the user terminal (111) tracks the session. Forexample, the user terminal (111) may use a web browser to track thesession via information maintained by the web browser (e.g., cookies).Alternatively or in combination, the interchange (101) may track thesession by maintaining information on the data storage facility (107).For example, after the user completes the log in process, theinterchange (101) may identify the user terminal (111) via identifierssuch as Internet address, Media Access Control address (MAC address), adifferent phone number (e.g., when the user terminal is a different cellphone), or other software or hardware identification number associatedwith the user terminal (111), such as a digital certificate; and theinterchange (101) may associate the phone number (123) with suchidentifiers until the expiration of a predetermined time period, orafter the user signals an end of the session using the user terminal(111) or using the mobile phone (117) at the phone number (123). In oneembodiment, the interchange (101) associates a plurality of identifiersof the user terminal (111) with the phone number (123) for the session.When at least one of the identifiers of the user terminal (111) ischanged, the interchange (101) may terminate the session automatically.

In FIG. 15, after the user terminal (111) submits the request to pay viathe phone number (123), the interchange (101) approves (345) the requestbased on the confirming of the identity of the user performed prior tothe request and processes (347) the request using funds associated withthe phone number (123). For example, the interchange (101) may transmitpremium messages, via a corresponding converter (131), to a mobile phone(117) at the phone number (123) to collect the funds, or receive premiummessages from a mobile phone (117) at the phone number (123) to collectthe funds. For example, the interchange (101) may determine the accountinformation (121) (e.g., an account identifier, such as a credit cardnumber, a bank account number, a debit card number, etc.) stored andassociated with the phone number (123) on the data storage facility(107) of the interchange (101) to charge the user using the accountinformation (121).

In one embodiment, in response to the payment request from the userterminal (111), the interchange (101) may send a notification message tothe mobile phone (117) at the phone number (123). The user is notrequired to provide a reply to complete the payment process. However,the user of the mobile phone (117) is provided with theoption/opportunity to reply and report a fraudulent use, or to cancelthe request (e.g., within a predetermined period of time).

In one embodiment, the data storage facility (107) stores a passwordassociated with the phone number (123) for authentication. In FIG. 16,after the interchange (101) receives (351) a password and a phone number(123) from a user terminal (111), the interchange (101) determines (352)whether the received password is the correct password for the phonenumber (123). If the received password is the correct password for thephone number (123), the interchange (101) associates (353) the userterminal (111) with the phone number (123) in the data storage facility(107). If, during the time period in which the user terminal (111) isassociated with the phone number (123), the interchange (101) receives(355) from the user terminal (111) a request to pay a payee (e.g., viathe user interface (201) illustrated in FIG. 8), the interchange (101)may approve (357) the request based on the confirmed association betweenthe user terminal (111) and the phone number (123) and pay the payeeusing funds associated with the phone number (123), without requiring aconfirmation via the mobile phone (117) at the phone number (123). Insome embodiments, after the user terminal (111) submits the phone number(123) to the interchange (101), the interchange (101) may request thepassword from the mobile phone (117) at the phone number (123).

In one embodiment, during the time period in which the user terminal(111) is associated with the phone number (123), the interchange (101)may automatically provide the phone number (123) in the text field (183)in the user interface (201) for submitting a payment request,illustrated in the FIG. 8, based on the association between the userterminal (111) and the phone number (123). The phone number (123) can beprovided by the interchange (101) in the text field (183) as a defaultinput. Alternatively, the interchange (101) may not provide the phonenumber (123) and may require the user to enter the phone number (123) inthe text field (183) for enhanced security. In some embodiments, theinterchange (101) may dynamically determine whether or not to presentthe phone number (123) in the text field (183) based on a transactionpattern associated with the phone number (123). For example, if thecurrent request matches the pattern, the interchange (101) presents thephone number (123) as the default input to simplify user interactions;otherwise, the interchange (101) does not provide the phone number (123)in the text field (183) for enhanced security.

In FIG. 17, after the interchange (101) receives (361) a phone number(123) from a user terminal (111), the interchange (101) communicates(363) with the user for an advance approval for the user terminal (111)via a mobile phone (117) at the phone number (123). For example, theinterchange (101) may communicate with the mobile phone (117) at thephone number (123) for the advance approval and/or communicate with theuser terminal (111) to confirm a password associated with the phonenumber (123).

In one embodiment, the advance approval is specific for the userterminal (111); and the interchange (101) stores identifiers of the userterminal (111) with the advance approval. For example, the interchange(101) may communicate with the user terminal (111) and/or the mobilephone (117) to associate the user terminal (111) with the phone number(123) for the advance approval of one or more subsequent paymentrequests.

In some embodiments, the advance approval is not limited to a particularuser terminal (111). For example, the user may directly use the mobilephone (117) at the phone number (123) to communicate the advanceapproval to the interchange (101) without having to identify the userterminal (111). Alternatively, the user may use a particular userterminal (111) to initiate the communications with the interchange (101)for the advance approval without limiting the advance approval tosubsequent payment requests for the same particular user terminal (111).

In one embodiment, the advance approval is associated with the phonenumber (123) on the data storage facility (107). When a request to payvia the funds associated with the phone number (123) is received, theadvance approval associated with the phone number (123) is identifiedand applied by the interchange (101). The user does not have toexplicitly identify the advance approval in making the payment request.

In one embodiment, the interchange (101) may assign an identificationcode for the advance approval for enhanced security. The user may usethe identification code in the payment request to explicitly identifythe advance approval.

In one embodiment, the advance approval specifies a time limit for theexpiration of the approval, a budget amount for one or more paymentrequests, a limit on the types of permitted products and/or services, atime window for permissible payment requests, a frequency forpermissible payment requests, and one or more limits based on certaincharacteristics of the payees (e.g., web addresses, countries,categories, etc.).

In one embodiment, the advance approval may specify some limits on thepermissible user terminals (111). For example, the advance approval maylimit the advance approval to user terminals located with certaingeographic areas. The interchange (101) may determine the geographicareas of the user terminals (111) based on the IP addresses of the userterminals (111), the access points for wireless local areacommunications, the base stations for cellular communications, etc.

After the advanced approval is associated with the phone number (123),the interchange (101) may receive (365) from the user terminal (111) arequest to pay a payee via the phone number (123). Based on the advanceapproval the interchange (101) may approve (367) the request and pay(369) the payee using funds associated with the phone number (123),without requiring a confirmation message from the user viacommunications with the mobile phone (117) at the phone number (123).

In some embodiments, the interchange (101) may use the transactionhistory (127) to determine whether or not to require a confirmationmessage from the user via communications with the mobile phone (117) atthe phone number (123). The transaction history (127) may include anumber of records of prior confirmed/approved payment requests.

For example, based on the records of prior payment requests theinterchange (101) may determine a payment pattern for the phone number(123), such as a list of frequently used user terminals (111) for thephone number (123), a range for typical payment amounts, a time periodof a day within which typical payment requests are received for thephone number (123), a list of frequently used payees paid via the phonenumber (123), a list of categories of services and/or productsfrequently paid via the phone number (123), a recent payment requestedconfirmed within a predetermined period of time, etc.

In FIG. 18, the interchange (101) processes (371) a plurality ofrequests to pay via a phone number (123). The interchange (101)processes (371) the requests via communicating with the mobile phone(117) at the phone number (123). For example, the interchange (101) maysend a message to the mobile phone (117) at the phone number (123) andrequest a reply to the message from the mobile phone (117). For example,the interchange (101) may request a PIN from the mobile phone (117) atthe phone number (123) to confirm the requests. For example, theinterchange (101) may send one-time codes representing the requests tothe mobile phone (117) or receive one-time codes representing therequests from the mobile phone (117).

The interchange (101) stores (373) transaction records of the paymentrequests and determines (375) a pattern of the payment requests.

Subsequently, when the interchange (101) receives (377) from a userterminal (111) a request to pay a payee via the phone number (123), theinterchange (101) determines (378) whether the request matches thepattern. If the request matches the pattern, the interchange (101) pays(379) the payee using funds associated with the phone number (123),without requiring a confirmation communicated via the mobile phone (117)at the phone number (123) to speed up the payment process. Theinterchange (101) may send a notification to the mobile phone (117) atthe phone number (123), without requiring a reply prior to making thepayment.

FIG. 19 shows a user interface to provide user information in connectionwith payment processing according to one embodiment. In FIG. 19, theuser interface (201) is presented after the interchange (101) finishesprocessing a payment request. For example, the user interface (201) inFIG. 19 may be displayed after the user is redirected from the websiteof the interchange (101) to the website of the payee on the server (113)(e.g., redirected from the user interface (201) illustrated in FIG. 11).

In one embodiment, the server (113) uses the user information (129)received from the interchange (101) to fill in the entry boxes (e.g.,221) as the default values to assist the user in the transaction. Forexample, the transaction may require a shipping address (221) and/orother information, such as shipping preferences, billing addresses, etc.

In one embodiment, the user information (129) is provided from theinterchange (101) to the server (113) during the interchange (101)redirecting the user to the server (113). For example, the userinformation (129) can be embedded or encoded in the uniform resourcelocator (URL) for redirecting the user to the server (113). In anotherembodiment, the server (113) queries the interchange (101) in relationwith the transaction to obtain the user information (129). For example,the server (113) may access an application programming interface (API)or a web service of the interchange (101) to obtain the user information(129).

In some embodiments, the interchange (101) operates in the background.After the user provides the phone number (123) to the server (113), theserver (113) accesses an application programming interface (API) or aweb service of the interchange (101) to process the payment and/orobtain the user information (129). The interchange (101) may secure theaccess to the information via communications with the mobile phone (117)at the phone number (123) in response to the server (113) accessing theAPI or web service of the interchange (101). Alternatively or incombination, the interchange (101) may secure the access to theinformation based on advance approval from the mobile phone (117),and/or based on the transaction patterns determined from the transactionhistory (127).

In some embodiments, the interchange (101) does not obtain funds fromthe user to pay the payee on behalf of the user of the mobile phone(117). Instead, the interchange (101) may provide the accountinformation (121) to the server (113) to allow the server (113) tocharge the user using the account information (121), as illustrated inFIG. 20.

FIG. 20 shows a user interface to provide user information to facilitatepayment processing according to one embodiment. In FIG. 20, the userinterface (201) is presented after the interchange (101) confirms thatthe user of the mobile phone (117) approves the transaction and afterthe interchange (101) provides the account information (121) to theserver (113).

In one embodiment, after obtaining the account information (121) fromthe interchange (101), the server (113) may present the accountinformation (121) in a form back to the user for confirmation and/ormodification, as illustrated in FIG. 20.

For example, in FIG. 20, the account type (e.g., visa) and the accountnumber are presented to the user. To improve security, the entry box(223) shows only a portion of the account number and hides the remainingportion of the account number. In some embodiments, the user is requiredto provide the portion of the account number that is hidden in the entrybox (223); and the server (113) matches the portion obtained from theinterchange (101) and the portion obtained from the user via the entrybox (223) to determine whether to accept the request.

In some embodiments, the interchange (101) may provide only a portion ofthe account number (e.g., the first or last portion of the accountnumber); and the user interface (201) requires the user to complete theremaining portion of the account number. In some embodiments, theinterchange (101) does not provide the account number; and the userinterface (201) requires the user to provide the account number.

In one embodiment, the interchange (101) also provides otherinformation, such as billing address (221), shipping address, etc. Suchinformation can be displayed in the user interface (201) as the defaultvalues for user confirmation. Thus, if the user accepts the defaultvalues, the user does not have to provide manual input, which providesconvenience and improves user experience.

In some embodiments, the server (113) may directly process the paymentusing the account number and/or complete the transaction using the userinformation (129) without presenting it to the user. For example, afterobtaining the account information (121) from the interchange (101), theserver (113) may communicate with the account server (125) to charge theuser for the purchased products and/or services; and after successfullycharging the user, the server (113) may further present the shippinginformation to the user (e.g., as illustrated in FIG. 19), withoutshowing the account information (121). In one embodiment, the userstores a preference option on the data storage facility (107) toindicate whether to request the interchange (101) to pay the servers(113) on behalf of the user, or to request the interchange (101) torelease the account information (121) to the server (113) when needed.In one embodiment, the user may specify such a preference when the userconfirms a payment request via the mobile phone (117) having the phonenumber (123).

FIGS. 21 and 22 illustrate user interfaces for authentication accordingto some embodiments.

In FIG. 21, the user interface (201) allows the user to provide thephone number (123) in the entry box (183) to start an authenticatedsession. In one embodiment, after the server (113) receives the phonenumber (123) from the entry box (183), the server (113) requests theinterchange (101) to confirm the identity of the user via the mobilephone (117).

For example, the interchange (101) may transmit an SMS message (or avoice message, or an email) to the mobile phone (117) at the phonenumber (123). When an appropriate reply to the SMS message is receivedback from the mobile phone (117), the interchange (101) determines thatthe user identity is confirmed.

For example, the interchange (101) may provide a one time code to theuser (e.g., via the server (113) or via the mobile phone (117)) andrequest the user to provide the one time code back to the interchange(101) via the mobile phone (117) (e.g., via an SMS message, via a voicecall, via a web request from the mobile phone (117) having the phonenumber (123), etc.). In some embodiments, the server (113) may generatethe one time code, and requests the user to submit the code to theinterchange (101) to complete the authentication process. Theinterchange (101) and/or the server (113) may determine if the codereceived from the mobile phone (117) matches the code provided (e.g.,the code generated by the server (113) or the code generated by theinterchange (101)).

In some embodiment, the one time code may be provided to the mobilephone (117) at the phone number (123) and the user is required toprovide the one time code back to the server (113) and/or theinterchange (101) to complete the authentication process.

In one embodiment, the server (113) (or the interchange (101)) mayrequest a correct password or personal identification number (PIN),transmitted from the mobile phone (117) having the phone number (123)via the interchange (101), to complete the authentication process.

In one embodiment, the authentication process serves as an advanceapproval for payment requests occurring in the session. For example,after the authentication process, the web session on the user terminal(111) is associated with the phone number (123); and before the websession is timed out (or the user signs out of the web session), paymentrequests can be processed using the phone number (123) without having toprovide the phone number (123) again from the user terminal (111) and/orto receive a communication from the user via the mobile phone (117) atthe phone number (123) to confirm the payment requests.

In one embodiment, the web session authenticated via the interchange(101) is associated with a particular web site of a merchant or serviceprovider. For example, the authenticated web session can be used as anadvanced approval for the particular website but not for a differentwebsite. In another embodiment, the web session authenticated via theinterchange (101) is associated with the user terminal (111) and isapplicable to different websites. For example, the authenticated websession initiated via one website may be used as an advance approval forother websites visited during the session.

In one embodiment, the user information (129) includes login credentialsof the user with the server (113). When the user entity is confirmedwith the mobile phone (117) having the phone number (123), the logincredentials of the user can be provided from the data storage facility(107) to the server (113) to start an authenticated session, asillustrated in FIG. 22.

In FIG. 22, the user may select the option (229) to sign in via themobile phone (117). Once the mobile phone option is selected in the userinterface (201) illustrated in FIG. 22, the user is directed to awebsite of the interchange (101), which obtains the mobile phone number(123) from the user. After communicating with the mobile phone (117) atthe phone number (123) to confirm the login request, the interchange(101) provides the corresponding login credentials of the user to server(113) to start an authenticated session on the server (113).

In one embodiment, after the server (113) obtains the login credentials(e.g., username and/or password) from the interchange (101), the server(113) may present the information in entry boxes (225 and 227) asdefault values, allowing the user to sign in by simply confirming therequest. For security, the password may be presented as a string ofhidden characters. The user may confirm the values and/or modify thevalues to sign into an authenticated session that is associated withboth the server (113) and the interchange (101).

In one embodiment, after the server (113) obtains the login credentials(e.g., username and/or password) from the interchange (101), the server(113) may sign the user in directly without presenting the logincredentials back to the user. Thus, the user does not have to provideadditional input to the server (113) to sign in, after the request isconfirmed via the interchange (101).

In one embodiment, the communications to confirm the user identity mayinvolve communications via the server (113). For example, a one timecode may be provided or received via the server (113) and the mobilephone (117) having the phone number (123). In some embodiments, the useris required to submit the password via the mobile phone (117) to signinto the server (113) for a web session running on the user terminal(111).

In one embodiment, the user may use the entry boxes (225 and 227) of theuser interface (201), shown in FIG. 22, to sign into a session at theserver (113) directly, without going through the interchange (101).During the session, when the payment is required, the user may providethe mobile phone number (123) to confirm the payment request via themobile phone (117).

Alternatively, during the session the server (113) may identify the userby the login information to the interchange (101), which then looks upthe phone number (123) via matching the login information and thenconfirming the payment request via communications with the mobile phone(117) at the phone number (123). Thus, during the session the user doesnot have to separately identify the phone number (123) in a paymentrequest.

In one embodiment, during the session, after the first payment requestis confirmed via communications with the mobile phone (117), the sessionis associated with both the server (113) and the interchange (101); andsubsequent payment requests in the session may not require confirmationvia the mobile phone (117).

In some embodiments, the user information (129) may not include logincredentials for the server (113). After the interchange (101) confirmsthe identity of the user via the mobile phone (117), the interchange(101) does not provide login credentials to the server (113); however,the interchange (101) may indicate to the server (113) that the identityof the user is confirmed and that the user is associated with the phonenumber (123); and the server (113) may start a session for an accountassigned to the phone number (123). In some embodiments, the interchange(101) may not even give the phone number (123) to the server (113);instead, a token (e.g., a user identifier) representing the phone number(123) may be used to identify the user to the server (113), and thetoken can be used in subsequent communications between the server (113)and the interchange (101) to identify the phone number (123) and theassociated user.

FIG. 23 shows a method to provide information according to oneembodiment. In FIG. 23, a phone number (123) is received (381) in a webrequest that identifies a website. The web request may be forwarded froma server (113) to the interchange (101), after the user provides thephone number (123) to the server (113). Alternatively, the web requestmay be received directly in the interchange (101) from the user terminal(111), after the server (113) forwards the request to the interchange(101). In some embodiments, the server (113) sends the web request tothe interchange (101) via an application programming interface (API) ora web service.

Using the phone number (123), the interchange (101) communicates (383)with a mobile phone (117) at the phone number (123) to obtain approvalfrom the user. In some embodiments, the interchange (101) obtains theadvance approval prior to the web request. The user information (129)may be an address of the user, a login credential of the user at a thirdparty website, or financial account information of the user, such as acredit card number, a debit card number, and a bank account number, etc.

In one embodiment, to obtain the approval the interchange (101)transmits a message to the mobile phone (117) at the phone number (123)and receives a reply to the message back from the mobile phone (117). Inone embodiment, the message and reply are transmitted via short messageservice (SMS).

In one embodiment, to obtain the approval the interchange (101)transmits a first code to the mobile phone (117) at the phone number(123), provides a web page in response to the web request, and receivesa second code in the web page in the server (113). The interchange (101)marches the first code with the second code to determine whether toapprove the providing of the user information (129) to the third partywebsite.

In one embodiment, to obtain the approval the interchange (101) providesa first code in a web page in response to the web request, receives asecond code from the mobile phone (117), and matches the first code withthe second code to determine whether to approve the providing of theuser information (129) to the third party website.

In one embodiment, to obtain the approval the interchange (101)receives, from the mobile phone (117) at the phone number (123), a firstpersonal identification number (PIN) (or password) and matches the firstPIN with a second PIN associated with the phone number (123) in the datastorage facility (107) to determine whether to approve the providing ofthe user information (129) to the third party web site.

In FIG. 23, if the web request is approved (385), the interchange (101)identifies (387) user information (129) associated with the phone number(123) and provides (389) the user information (129) to the web site.

In one embodiment, the interchange (101) further makes a payment to thethird party website in accordance with the web request, using fundsassociated with the phone number (123) of the user. The interchange(101) may collect the funds via at least one premium message originatedfrom or terminated at the mobile phone (117) at the phone number (123),or by charging the user using the account information (121) associatedwith the phone number (123).

FIG. 24 shows a data processing system, which can be used in variousembodiments. While FIG. 24 illustrates various components of a computersystem, it is not intended to represent any particular architecture ormanner of interconnecting the components. Some embodiments may use othersystems that have fewer or more components than those shown in FIG. 24.

In one embodiment, each of the interchange (101), the data storagefacility (107), the controllers (115), the mobile phones (117), the userterminals (111), the account server (125) and the servers (113) can beimplemented as a data processing system, with fewer or more components,as illustrated in FIG. 24.

In FIG. 24, the data processing system (401) includes an inter-connect(402) (e.g., bus and system core logic), which interconnects amicroprocessor(s) (403) and memory (408). The microprocessor (403) iscoupled to cache memory (404) in the example of FIG. 24.

The inter-connect (402) interconnects the microprocessor(s) (403) andthe memory (408) together and also interconnects them to a displaycontroller, display device (407), and to peripheral devices such asinput/output (I/O) devices (405) through an input/output controller(s)(406).

Typical I/O devices include mice, keyboards, modems, network interfaces,printers, scanners, video cameras and other devices which are well knownin the art. In some embodiments, when the data processing system is aserver system, some of the I/O devices, such as printer, scanner, mice,and/or keyboards, are optional.

The inter-connect (402) may include one or more buses connected to oneanother through various bridges, controllers and/or adapters. In oneembodiment, the I/O controller (406) includes a USB (Universal SerialBus) adapter for controlling USB peripherals, and/or an IEEE-1394 busadapter for controlling IEEE-1394 peripherals.

The memory (408) may include ROM (Read Only Memory), volatile RAM(Random Access Memory), and non-volatile memory, such as hard drive,flash memory, etc.

Volatile RAM is typically implemented as dynamic RAM (DRAM) whichrequires power continually in order to refresh or maintain the data inthe memory. Non-volatile memory is typically a magnetic hard drive, amagnetic optical drive, an optical drive (e.g., a DVD RAM), or othertype of memory system which maintains data even after power is removedfrom the system. The non-volatile memory may also be a random accessmemory.

The non-volatile memory can be a local device coupled directly to therest of the components in the data processing system. A non-volatilememory that is remote from the system, such as a network storage devicecoupled to the data processing system through a network interface suchas a modem or Ethernet interface, can also be used.

In this description, various functions and operations may be describedas being performed by or caused by software code to simplifydescription. However, those skilled in the art will recognize that whatis meant by such expressions is that the functions result from executionof the code/instructions by a processor, such as a microprocessor.Alternatively, or in combination, the functions and operations can beimplemented using special purpose circuitry, with or without softwareinstructions, such as using Application-Specific Integrated Circuit(ASIC) or Field-Programmable Gate Array (FPGA). Embodiments can beimplemented using hardwired circuitry without software instructions, orin combination with software instructions. Thus, the techniques arelimited neither to any specific combination of hardware circuitry andsoftware, nor to any particular source for the instructions executed bythe data processing system.

While some embodiments can be implemented in fully functioning computersand computer systems, various embodiments are capable of beingdistributed as a computing product in a variety of forms and are capableof being applied regardless of the particular type of machine orcomputer-readable media used to actually effect the distribution.

At least some aspects disclosed can be embodied, at least in part, insoftware. That is, the techniques may be carried out in a computersystem or other data processing system in response to its processor,such as a microprocessor, executing sequences of instructions containedin a memory, such as ROM, volatile RAM, non-volatile memory, cache or aremote storage device.

Routines executed to implement the embodiments may be implemented aspart of an operating system or a specific application, component,program, object, module or sequence of instructions referred to as“computer programs.” The computer programs typically include one or moreinstructions set at various times in various memory and storage devicesin a computer, and that, when read and executed by one or moreprocessors in a computer, cause the computer to perform operationsnecessary to execute elements involving the various aspects.

A machine readable medium can be used to store software and data whichwhen executed by a data processing system causes the system to performvarious methods. The executable software and data may be stored invarious places including for example ROM, volatile RAM, non-volatilememory and/or cache. Portions of this software and/or data may be storedin any one of these storage devices. Further, the data and instructionscan be obtained from centralized servers or peer to peer networks.Different portions of the data and instructions can be obtained fromdifferent centralized servers and/or peer to peer networks at differenttimes and in different communication sessions or in a same communicationsession. The data and instructions can be obtained in entirety prior tothe execution of the applications. Alternatively, portions of the dataand instructions can be obtained dynamically, just in time, when neededfor execution. Thus, it is not required that the data and instructionsbe on a machine readable medium in entirety at a particular instance oftime.

Examples of computer-readable media include but are not limited torecordable and non-recordable type media such as volatile andnon-volatile memory devices, read only memory (ROM), random accessmemory (RAM), flash memory devices, floppy and other removable disks,magnetic disk storage media, optical storage media (e.g., Compact DiskRead-Only Memory (CD ROMS), Digital Versatile Disks (DVDs), etc.), amongothers.

The computer-readable media may store the instructions. The instructionsmay also be embodied in digital and analog communication links forelectrical, optical, acoustical or other forms of propagated signals,such as carrier waves, infrared signals, digital signals, etc.

In general, a tangible machine readable medium includes any mechanismthat provides (i.e., stores and/or transmits) information in a formaccessible by a machine (e.g., a computer, network device, personaldigital assistant, manufacturing tool, any device with a set of one ormore processors, etc.).

In various embodiments, hardwired circuitry may be used in combinationwith software instructions to implement the techniques. Thus, thetechniques are neither limited to any specific combination of hardwarecircuitry and software nor to any particular source for the instructionsexecuted by the data processing system.

Although some of the drawings illustrate a number of operations in aparticular order, operations which are not order dependent may bereordered and other operations may be combined or broken out. While somereordering or other groupings are specifically mentioned, others will beapparent to those of ordinary skill in the art and so do not present anexhaustive list of alternatives. Moreover, it should be recognized thatthe stages could be implemented in hardware, firmware, software or anycombination thereof.

In the foregoing specification, the disclosure has been described withreference to specific exemplary embodiments thereof. It will be evidentthat various modifications may be made thereto without departing fromthe broader spirit and scope as set forth in the following claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative sense rather than a restrictive sense.

What is claimed is:
 1. A computer-implemented method, comprising:presenting, by at least one server computer, a website with a field forentering a phone number of a user; receiving at the server computer aweb request including an amount and the phone number of the user enteredby the user in relation to a transaction of the user at the web site;identifying a user account on a data storage facility coupled to theserver computer, based on the phone number entered by the user; andcharging the account based on the amount received in the web request. 2.The method of claim 1, further comprising: communicating with a mobilephone of the user at the phone number of the user to obtain approval forthe charging of the account based on the amount.
 3. The method of claim2, wherein the communicating comprises: transmitting a message to themobile phone at the phone number; and receiving a reply to the messageback from the mobile phone.
 4. The method of claim 3, wherein themessage and reply are transmitted via short message service (SMS). 5.The method of claim 2, wherein the communicating comprises: transmittinga first code to the mobile phone at the phone number; providing a webpage in response to the web request; and receiving a second code in theweb page in the server computer; wherein the first code is matched withthe second code to determine whether to approve the providing of theuser information to the third party website.
 6. The method of claim 2,wherein the communicating comprises: providing from the server computera first code in a web page in response to the web request; and receivinga second code from the mobile phone; wherein the first code is matchedwith the second code to determine whether to approve the providing ofthe user information to the third party website.
 7. The method of claim1, further comprising: receiving at the server a first personalidentification number (PIN); wherein the first PIN is matched with asecond PIN associated with the phone number in the data storage facilityto determine whether to approve the charging of the account.
 8. Themethod of claim 2, further comprising: making a payment to a third partywebsite in accordance with the web request, using funds associated withthe account.
 9. The method of claim 8, further comprising: collectingthe funds via at least one premium message originated from or terminatedat the mobile phone at the phone number.
 10. The method of claim 1,further comprising: identifying user information stored in the account;and transmitting the user information to the third party website. 11.The method of claim 10, wherein the user information includes an addressof the user at the third party website.